home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 4
/
QRZ Ham Radio Callsign Database - Volume 4.iso
/
digests
/
policy
/
940188.txt
< prev
next >
Wrap
Internet Message Format
|
1994-11-13
|
22KB
Date: Sat, 30 Apr 94 04:30:08 PDT
From: Ham-Policy Mailing List and Newsgroup <ham-policy@ucsd.edu>
Errors-To: Ham-Policy-Errors@UCSD.Edu
Reply-To: Ham-Policy@UCSD.Edu
Precedence: Bulk
Subject: Ham-Policy Digest V94 #188
To: Ham-Policy
Ham-Policy Digest Sat, 30 Apr 94 Volume 94 : Issue 188
Today's Topics:
FCC computers
FD Logging software.
Homebrew 610 forms
Homebrew 610 forms, take 2
Internet -> packet gateway policy
Ooops.
Send Replies or notes for publication to: <Ham-Policy@UCSD.Edu>
Send subscription requests to: <Ham-Policy-REQUEST@UCSD.Edu>
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the Ham-Policy Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/ham-policy".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Fri, 29 Apr 94 13:35:21 EDT
From: ihnp4.ucsd.edu!library.ucla.edu!europa.eng.gtefsd.com!news.umbc.edu!eff!neoucom.edu!ns.mcs.kent.edu!kira.cc.uakron.edu!malgudi.oar.net!hypnos!voxbox!jgrubs@network.ucsd.edu
Subject: FCC computers
To: ham-policy@ucsd.edu
alanb@sr.hp.com (Alan Bloom) writes:
> David Stockton (dstock@hpqmoca.sqf.hp.com) wrote:
> : Jim Grubs, W8GRT (jgrubs@voxbox.norden1.com) wrote:
>
>
> : : I don't know, but rumor has it the Smithsonian wants it when the
> : : FCC gets a new one. :)
>
> : Silly question..... with 12+ week delays etc, and thinking of the
> : phone bills generated by having to phone ARRL, VEC etc for permission
> : before phoning the FCC, would it be worthwhile for US amateurs, VECs and
> : the ARRL to raise funds for a modest PC with a moderately big disc and
> : volunteer-written software, and then *GIVE* it to the FCC as a donation ?
>
> I wouldn't help unless we were willing to put in a major effort to re-write
> the software to go with it. It's the same problem NASA has with the space
> shuttle. Sure, the computer hardware is woefully out-of-date, but a new
> computer would require rewriting and then re-flight-qualifying the software.
> A serious software bug in the FCC's computer wouldn't be QUITE as
> disasterous as one in the space shuttle, but it wouldn't be too nifty either.
>
> There are reliability questions as well. I'm very sensitive to this
> having had a hard disc crash on my PC a few weeks ago :=(
>
> It still might make sense for ARRL to buy the FCC a high-reliability
> computer and hire a professional programmer to write them some software.
>
> AL N1AL
>
It might make still more sense to turn the job over to the ARRL,
a la the proposal for Canada. India has ALWAYS used this system,
and so far as I know it has always worked well.
/----------------------------------------------------------------------\
| Jim Grubs, W8GRT Voxbox Enterprises Tel.: 419/882-2697 |
| jgrubs@voxbox.norden1.com 6817 Maplewood Ave. |
| Fido: 1:234/1.0 Sylvania, Ohio 43560 |
\-+--------------------------------------------------------------------/
------------------------------
Date: 29 Apr 1994 13:26 CDT
From: ihnp4.ucsd.edu!galaxy.ucr.edu!library.ucla.edu!europa.eng.gtefsd.com!howland.reston.ans.net!cs.utexas.edu!swrinde!news.uh.edu!elroy.uh.edu!st3qi@network.ucsd.edu
Subject: FD Logging software.
To: ham-policy@ucsd.edu
I am looking for Field Day logging software that will work on an XT machine.
I have KB0ZP logging, but I can't get it to work on the XT. Does anyone
have any leads on some simple, shareware FD logging programs?
-Brad Killebrew N5LJV
-st3qi@jetson.uh.edu
-President, Univ of Houston ARC
------------------------------
Date: 29 Apr 94 09:00:51 -0500
From: yale.edu!noc.near.net!news.tufts.edu!news.hnrc.tufts.edu!jerry@yale.arpa
Subject: Homebrew 610 forms
To: ham-policy@ucsd.edu
In article <ggsJRR#@quack.kfu.com>, nsayer@quack.kfu.com (Nick Sayer) writes:
>
> More to the point, is there anything wrong with this:
> %%
> %% This version of the form may (or may not) be out of date. It
> %% certainly dates back to before 1990. Apart from that, I'm not sure
> %% of the pedigree of my master. I do know that it is an original
> %% Govt. Printing Office rendition.
I am not a VEC.
My understanding is that a new 610 became available on March 1, 1994 and, for
the first time, the FCC has decided that it will no longer accept the older
versions.
------------------------------
Date: 30 Apr 1994 04:23:21 UTC
From: ihnp4.ucsd.edu!library.ucla.edu!psgrain!quack!quack.kfu.com!nsayer@network.ucsd.edu
Subject: Homebrew 610 forms, take 2
To: ham-policy@ucsd.edu
Many thanks to the League (I never thought I'd hear that coming out of
my keyboard/mouth) for shipping me a new 610 form. Over the last 4
hours or so I have managed a first cut at the front. It is included
below.
The back is going to be a cast iron bitch. There are blobs of free-form
text that's supposed to be right justified. I'm going to ask the FCC
if they won't let it slide and accept forms with blank backs for those
cases (the vast majority, I'm sure) where the back would otherwise be
blank (it's the doctor's certification for those too ill/trashed to
take the 13 and 20 wpm tests). They're the Government, so they're likely
to say 'no'. But in any case, while I'm doing that, you all might take
a look and see if you can spot any typos or anything.
Thanks.
%!
%% FCC610A.PS
%% Federal Communications Commission form 610, side 1
%% Version 2.0
%% Written by Nick Sayer, N6QQQ
%% I don't think I can claim copyright on this since it is a federal
%% form.
%%
%% THIS VERSION HAS NOT BEEN SUBMITTED TO THE FCC FOR APPROVAL, NOR HAS
%% IT BEEN ACTUALLY USED IN APPLICATIONS TO THE COMMISSION. IF YOU USE
%% THIS FORM AND THE FCC KICKS IT BACK, IT'S NOT MY FAULT. I would like
%% any feedback with regards to acceptability of forms generated by
%% this code.
%%
%% One hint: The paper color is critical. I have submitted 610 forms
%% photocopied onto 'Goldenrod' paper and have had them accepted,
%% but white won't work. The FCC uses paper color to sort the forms
%% from various services out more easily or something.
%%
%% The source for this form is the 11/93 version of the form.
%% The original indicia (here deleted per FCC policy) said
%% 3060-0033, expires 08/31/95.
%%
%% The form was carefully measured with a ruler to the nearest millimeter.
%% The font used throughout is a sans serif font. Helvetica looks as
%% good as any other, but if there's an official font, I'd love to hear
%% about it.
%%
%% Here are the differences you may note in the form:
%%
%% 1. OMB notation at upper left omitted.
%% This in keeping with FCC policy for privately generated forms
%%
%% 2. Possible measurement errors.
%% I only measured to the nearest 1 mm. Some lines had to be moved
%% very slightly to make room for the granularity of postscript's
%% font scaling machinery (especially in section 2A).
%%
%% 3. The text in the second certification section in section 1
%% is supposed to be right justified.
%% Life is too short.
%%
%% 4. The text in both certification sections in section 1 is a little
%% smaller than on the original form.
%% The problem is that 8 point is too big, and my postscript platform
%% at least (ghostscript 2.6.1) won't take real arguments to scalefont
%% (it internally rounds).
%%
%% 5. Helvetica is the closest font I could find to the one the FCC
%% used. It's not an exact match. Their font is certainly a
%% sans-serif font. I think it's close enough.
%%
%% Any other differences are probably bugs.
%%
%% Ironically, I can't use this file, since my (DeskJet) printer has a
%% 1/2 inch unprintable border on the bottom, which cuts off the bottom
%% of the signature area. C'est la guerre.
/inch { 72 mul } def
/cm { 2.54 div inch } def
/mm { 25.4 div inch } def
/BOLD-FONT (Helvetica-Bold) findfont def
/NORMAL-FONT (Helvetica) findfont def
% Everything is relative to the bottom-left corner of the main box.
% So to make it fit on the page, we have to shove it around a bit.
.7 cm 1.5 cm translate
% There are two very thick boxes near the top and middle
/headerbox % x y --
{
moveto
gsave
2 setlinewidth
198 mm 0 rlineto 0 6 mm rlineto -198 mm 0 rlineto closepath stroke
grestore gsave % to rescue the currentpoint.
35 mm 0 rmoveto 0 6 mm rlineto 198 35 2 mul sub mm 0 rmoveto 0 -6 mm
rlineto stroke
grestore gsave % again...
.95 setgray 1 1 rmoveto 35 mm 2 sub 0 rlineto 0 6 mm 2 sub rlineto
-35 mm 2 add 0 rlineto closepath fill
grestore gsave % one more time.
.95 setgray 198 mm 1 sub 1 rmoveto -35 mm 2 add 0 rlineto 0 6 mm 2 sub
rlineto 35 mm 2 sub 0 rlineto closepath fill
grestore
} def
0 232 mm headerbox
0 101 mm headerbox
% The rest of the lines are a half point wide
.5 setlinewidth
% The main box
newpath 0 232 mm moveto 0 0 lineto 198 mm 0 lineto 198 mm 232 mm lineto
stroke
% Now all the full-length horizontal lines
/full-line % y --
{
dup 0 exch moveto 198 mm exch lineto stroke
} def
11 mm full-line
24 mm full-line
37 mm full-line
45 mm full-line
120 mm full-line
131 mm full-line
138 mm full-line
150 mm full-line
157 mm full-line
168 mm full-line
210 mm full-line
220 mm full-line
% Now all the vertical lines dividing those stripes
66 mm 0 moveto 66 mm 37 mm lineto
99 mm 0 moveto 99 mm 37 mm lineto
169 mm 0 moveto 169 mm 37 mm lineto
stroke
119 mm 45 mm moveto 119 mm 101 mm lineto stroke
155 mm 107 mm moveto 155 mm 120 mm lineto stroke
155 mm 138 mm moveto 155 mm 150 mm lineto stroke
88 mm 157 mm moveto 88 mm 168 mm lineto stroke
139 mm 157 mm moveto 139 mm 168 mm lineto stroke
84 mm 210 mm moveto 84 mm 232 mm lineto stroke
137 mm 210 mm moveto 137 mm 232 mm lineto stroke
158 mm 210 mm moveto 158 mm 232 mm lineto stroke
% Now all the horizontal lines dividing up the resulting cubes
0 mm 68 mm moveto 119 mm 68 mm lineto stroke
0 mm 56 mm moveto 119 mm 56 mm lineto stroke
% Now once again we divide up the resulting slices
62 mm 45 mm moveto 62 mm 56 mm lineto stroke
% Now we start scribbling. TOP SECTION
/center-text % string --
{
dup stringwidth pop 2 div currentpoint pop exch sub currentpoint
exch pop moveto show
} def
NORMAL-FONT 8 scalefont setfont
0 253 mm moveto (FEDERAL COMMUNICATIONS COMMISSION) show
0 250 mm moveto (GETTYSBURG, PENNSYLANIA) show
BOLD-FONT 14 scalefont setfont
99 mm 246 mm moveto (APPLICATION FORM 610 FOR) center-text
99 mm 240 mm moveto (AMATEUR OPERATOR/PRIMARY STATION LICENSE) center-text
BOLD-FONT 10 scalefont setfont
99 mm 234 mm moveto
(SECTION 1 - TO BE COMPLETED BY APPLICANT \(See instructions\))
center-text
99 mm 103 mm moveto
(SECTION 2 - TO BE COMPLETED BY ALL ADMINISTERING VE's)
center-text
BOLD-FONT 8 scalefont setfont
99 mm 38 mm moveto
(WITH THE INSTRUCTIONS PROVIDED BY THE COORDINATING VEC AND THE FCC)
center-text
99 mm 42 mm moveto
(I CERTIFY THAT I HAVE COMPLIED WITH THE ADMINISTERING VE REQUIREMENTS IN PART 97 OF THE COMMISSION'S RULES AND)
center-text
/box % --
{ currentpoint newpath moveto .3 cm 0 cm rlineto 0 cm .3 cm rlineto
-.3 cm 0 cm rlineto closepath stroke }
def
NORMAL-FONT 8 scalefont setfont
1 mm 229 mm moveto (1. Print or type last name) show
65 mm 229 mm moveto (Suffix) show
85 mm 229 mm moveto (First name) show
138 mm 229 mm moveto (Middle initial) show
159 mm 229 mm moveto (2. Date of birth) show
1 mm 217 mm moveto (3. Mailing address \(Number and street\)) show
85 mm 217 mm moveto (City) show
138 mm 217 mm moveto (State code) show
159 mm 217 mm moveto (ZIP code) show
/date-line
{
gsave
0 mm 6 rmoveto
[ 5 mm 1 mm 5 mm 2 mm ] 0 setdash
39 mm 0 rlineto stroke
grestore gsave
[ 0 11 mm 2 mm 11 mm 2 mm 11 mm ] 1 setdash
0 mm 12 rmoveto
35 mm 0 rlineto stroke
grestore gsave
NORMAL-FONT 8 scalefont setfont
(month) show
grestore gsave
15 mm 0 rmoveto
NORMAL-FONT 8 scalefont setfont
(day) show
grestore gsave
26 mm 0 rmoveto
NORMAL-FONT 8 scalefont setfont
(year) show
grestore
} def
160 mm 221 mm moveto date-line
1 mm 207 mm moveto (4. I HEREBY APPLY FOR \(make an X in the ) show
(appropriate box\(es\)\):) show
7 mm 199 mm moveto (4A. ) show 13 mm 199 mm moveto box
BOLD-FONT 10 scalefont setfont
18 mm 199 mm moveto (EXAMINATION ) show
NORMAL-FONT 8 scalefont setfont
( for a new license) show
7 mm 190 mm moveto (4B. ) show 13 mm 190 mm moveto box
BOLD-FONT 10 scalefont setfont
18 mm 190 mm moveto (EXAMINATION ) show
NORMAL-FONT 8 scalefont setfont
( for upgrade of my operator license) show
18 mm 187 mm moveto (class) show
7 mm 180 mm moveto (4C. ) show 13 mm 180 mm moveto box
BOLD-FONT 10 scalefont setfont
18 mm 180 mm moveto (CHANGE ) show
NORMAL-FONT 8 scalefont setfont
( my name on my license to my new) show
18 mm 177 mm moveto (name in item 1. My former name was:) show
18 mm 172 mm moveto 94 mm 172 mm lineto stroke
18 mm 169 mm moveto (\(Last name\)) show
41 mm 169 mm moveto (\(Suffix\)) show
57 mm 169 mm moveto (\(First name\)) show
86 mm 169 mm moveto (\(MI\)) show
110 mm 199 mm moveto (4D. ) show 116 mm 199 mm moveto box
BOLD-FONT 10 scalefont setfont
121 mm 199 mm moveto (CHANGE ) show
NORMAL-FONT 8 scalefont setfont
( my mailing address on my license to) show
121 mm 196 mm moveto (my new address in item 3.) show
110 mm 190 mm moveto (4E. ) show 116 mm 190 mm moveto box
BOLD-FONT 10 scalefont setfont
121 mm 190 mm moveto (CHANGE ) show
NORMAL-FONT 8 scalefont setfont
( my station call sign systematically) show
121 mm 187 mm moveto (\(See instructions\)) show
121 mm 184 mm moveto (Applicant's initials) show
110 mm 173 mm moveto (4F. ) show 116 mm 173 mm moveto box
BOLD-FONT 10 scalefont setfont
121 mm 173 mm moveto (RENEWAL ) show
NORMAL-FONT 8 scalefont setfont
( of my license) show
1 mm 165 mm moveto (5.) show
5 mm 165 mm moveto
(Unless you are requesting a new license, attach the) show
5 mm 162 mm moveto
(original or a photocopy of your license to the back of this) show
5 mm 159 mm moveto
(Form 610 and complete items 5A and 5B.) show
90 mm 165 mm moveto (5A. Call sign shown on license) show
141 mm 165 mm moveto (5B. Operator class shown on license) show
1 mm 154 mm moveto (6.) show
5 mm 154 mm moveto (Would an FCC grant of your request be an ) show
(action that may) show
5 mm 151 mm moveto (have a significant environmental effect?) show
BOLD-FONT 10 scalefont setfont
110 mm 151 mm moveto box
115 mm 151 mm moveto (NO) show
134 mm 151 mm moveto box
139 mm 151 mm moveto (YES ) show
NORMAL-FONT 8 scalefont setfont
0 1 mm rmoveto
( \(Attach required statement\)) show
1 mm 147 mm moveto (7.) show
5 mm 147 mm moveto (If you have filed another Form 610 that we) show
5 mm 144 mm moveto (have not acted upon, complete items 7A) show
5 mm 141 mm moveto (and 7B.) show
68 mm 147 mm moveto (7A. Purpose of other form) show
157 mm 147 mm moveto (7B. Date filed) show
160 mm 139 mm moveto date-line
NORMAL-FONT 6 scalefont setfont
99 mm 135 mm moveto
(WILLFUL FALSE STATEMENTS MADE ON THIS FORM ARE PUNISHABLE BY FINE AND/OR IMPRISONMENT, \(U.S. CODE, TITLE 18, SECTION 1001\), AND/OR REVOCATION OF)
center-text
99 mm 132 mm moveto
(ANY STATION LICENSE OR CONSTRUCTION PERMIT \(U.S. CODE, TITLE 47, SECTION 312\(A\)\(1\)\) AND/OR FORFEITURE \(U.S. CODE, TITLE \(47, SECTION 503\).)
center-text
NORMAL-FONT 6 scalefont setfont
2 mm 128 mm moveto
(I CERITFY THAT ALL STATEMENTS AND ATTACHMENTS ARE TRUE, COMPLETE, ) show
(AND CORRECT TO THE BEST OF MY KNOWLEDGE AND BELIEF AND ARE MADE IN GOOD)
show
2 mm 125 mm moveto
(FAITH; THAT I AM NOT A REPRESENTATIVE OF A FOREIGN GOVERNMENT, ) show
(THAT I WAIVE ANY CLAIM TO THE USE OF A PARTICULAR FREQUENCY REGARDLESS OF)
show
2 mm 122 mm moveto
(PRIOR USE BY LICENSE OR OTHERWISE; AND THAT THE STATION TO BE ) show
(LICENSED WILL BE INACCESSIBLE TO UNAUTHORIZED PERSONS.) show
NORMAL-FONT 8 scalefont setfont
1 mm 117 mm moveto (8.) show
5 mm 117 mm moveto
(Signature of applicant \(Do not print, type or stamp.) show
(\) \(Must match name in item 1.\)) show
157 mm 117 mm moveto (9. Date signed) show
160 mm 108 mm moveto date-line
BOLD-FONT 14 scalefont setfont
6 mm 110 mm moveto (x) show
10 mm 110 mm moveto 152 mm 110 mm lineto stroke
% BOTOM SECTION
NORMAL-FONT 8 scalefont setfont
1 mm 97 mm moveto (A.) show
5 mm 97 mm moveto (Applicant is qualified for operator license class:)
show
120 mm 97 mm moveto (B. VEC receipt date:) show
1 mm 64 mm moveto (C.) show
5 mm 64 mm moveto (Name of Volunteer-Examiner Coordinator \(VEC\):) show
1 mm 53 mm moveto (D.) show
5 mm 53 mm moveto (Date of VEC coordinated examination) show
5 mm 50 mm moveto (session:) show
63 mm 53 mm moveto (E. Examination session location:) show
/ve-line % y --
{
dup 67 mm exch moveto (VE's station call sign) show
dup 100 mm exch moveto (VE's signature \(must match name\)) show
170 mm exch moveto (Date signed) show
} def
1 mm 34 mm moveto (1st VE's name \(Print First, MI, Last, Suffix\)) show
34 mm ve-line
1 mm 21 mm moveto (2nd VE's name \(Print First, MI, Last, Suffix\)) show
21 mm ve-line
1 mm 8 mm moveto (3rd VE's name \(Print First, MI, Last, Suffix\)) show
8 mm ve-line
BOLD-FONT 9 scalefont setfont
4 mm 92 mm moveto box
11 mm 92 mm moveto (NOVICE) show
50 mm 92 mm moveto (\(Elements 1\(A\), 1\(B\) and 2\)\)) show
4 mm 88 mm moveto box
11 mm 88 mm moveto (TECHNICIAN) show
50 mm 88 mm moveto (\(Elements 2 and 3\(A\)\)) show
4 mm 84 mm moveto box
11 mm 84 mm moveto (TECHNICIAN PLUS) show
50 mm 84 mm moveto (\(Elements 1\(A\), 1\(B\), or 1\(C\), 2 and 3\(A\)\)) show
4 mm 80 mm moveto box
11 mm 80 mm moveto (GENERAL) show
50 mm 80 mm moveto (\(Elements 1\(B\) or 1\(C\), 2, 3\(A\), and 3\(B\)\)) show
4 mm 76 mm moveto box
11 mm 76 mm moveto (ADVANCED) show
50 mm 76 mm moveto (\(Elements 1\(B\) or 1\(C\), 2, 3\(A\), 3\(B\),) show
( and 4\(A\)\)) show
4 mm 72 mm moveto box
11 mm 72 mm moveto (AMATEUR EXTRA) show
50 mm 72 mm moveto (\(Elements 1\(C\), 2, 3\(A\), 3\(B\), 4\(A\)) show
( and 4\(B\)\)) show
% Finally, right justify this bit at the bottom
NORMAL-FONT 8 scalefont setfont
/right-justify
{
dup stringwidth pop currentpoint pop exch sub currentpoint
exch pop moveto show
} def
198 mm -3 mm moveto (FCC Form 610) right-justify
198 mm -6 mm moveto (November 1993) right-justify
% This is optional. Uncomment it if you wish
% 0 -3 mm moveto
% (No U.S. Government funds were used to print this document.) show
% WHEW! Half way home!
showpage
%----- If it's from here on, it ain't part of the file.
--
Nick Sayer <nsayer@quack.kfu.com> |
N6QQQ @ N0ARY.#NOCAL.CA.USA.NOAM | AMD
+1 408 249 9630, log in as 'guest' | Inside
PGP 2.2 key and geek code via finger |
------------------------------
Date: 29 Apr 1994 16:51:24 GMT
From: news.mentorg.com!newsgw.mentorg.com!hpbab33.mentorg.com!wv.mentorg.com!hanko@uunet.uu.net
Subject: Internet -> packet gateway policy
To: ham-policy@ucsd.edu
In article <JKA.94Apr26101230@mustang.ece.cmu.edu>, jka@ece.cmu.edu (Jay Adams) writes:
|>
|> A local amateur radio operator recently complained about my use of an
|> internet to packet gateway, asserting that such a gateway constitutes
|> use of the amateur packet network by non-amateurs. I am a licensed
|> amateur, but that's not the point. I assume that someone has worked
|> out all the legal technicalities of these gateways. What should I
|> tell this guy to make him leave me alone?
|>
|> - Jay
Hope he complains about any NTS traffic as well ...
In my mind, the proper response to these "network cops"
goes along the lines of "Stick it in you ear, idiot."
... Hank
--
Hank Oredson @ Mentor Graphics
Internet : hank_oredson@mentorg.com
Amateur Radio: W0RLI@W0RLI.OR.USA.NOAM
------------------------------
Date: 29 Apr 1994 13:29 CDT
From: ihnp4.ucsd.edu!galaxy.ucr.edu!library.ucla.edu!europa.eng.gtefsd.com!howland.reston.ans.net!cs.utexas.edu!swrinde!news.uh.edu!elroy.uh.edu!st3qi@network.ucsd.edu
Subject: Ooops.
To: ham-policy@ucsd.edu
Oops. Disregard the last message, I posted it in the wrong area.
-Brad Killebrew N5LJV
-st3qi@jetson.uh.edu
-President, Univ of Houston ARC
------------------------------
Date: Fri, 29 Apr 1994 14:24:14 GMT
From: ihnp4.ucsd.edu!swrinde!elroy.jpl.nasa.gov!ncar!csn!cherokee!walter!dancer.cc.bellcore.com!not-for-mail@network.ucsd.edu
To: ham-policy@ucsd.edu
References <2p40p5$isa@abyss.West.Sun.COM>, <gganderson.357.0@augustana.edu>, <CouB4J.E3z@world.std.com>mai
Subject : Re: /KT (was /AA? (I'm confused))
In article <CouB4J.E3z@world.std.com>,
David R Tucker <drt@world.std.com> wrote:
>: Don't forget that a Tech that becomes Tech+ has the /KT suffix
>: they can (should) use when in the HF.
>
>Well, the rule specifies that KT is to be used when a Novice upgrades
>to Technician.
True, and the tech who upgrades to tech+ does not use the KT suffix
on HF. Why, because there isn't a new license issued to reflect
the Texh+ change. The use of the various suffix IDs is to indicate
the "temporary" operating approval between passing the test elements
and actual receipt of a new license. Thus, no suffix is needed for
tech+ from tech because there isn't any new license to wait for.
Just a small clarification of detail.
Standard Disclaimer- Any opinions, etc. are mine and NOT my employer's.
-----------------------------------------------------------------------
Bill Sohl (K2UNK) BELLCORE (Bell Communications Research, Inc.)
Morristown, NJ email via UUCP bcr!cc!whs70
201-829-2879 Weekdays email via Internet whs70@cc.bellcore.com
------------------------------
End of Ham-Policy Digest V94 #188
******************************